Double-Take Availability Release Notes
Double-Take Availability version 4.6.0, December 23, 2009
© 1996-2010 Double-Take Software, Inc. All rights reserved.
This readme file contains last minute release notes about Double-Take Availability that are not included in the user documentation. The user documentation is available on the product CD and in the installation directory after you have installed Double-Take Availability.
Be sure to check the readme file posted on the product updates download page of the Double-Take Software support web site for the latest release notes. The readme file contained in the self-extracting zip file or on the CD may not contain all of the most recent information.
Contents
Overview
This release is an updated release that includes, but may not be limited to, the following features.
- Operating system/distribution support—Double-Take Availability now supports Novell SUSE Linux Enterprise Server 9.3, 9.4, and 11.
- Activation codes—Improvements have been made to the activation codes for Double-Take Availability licensing.
This release is an updated release that supersedes all previous releases. You can safely upgrade to this release from any previous Double-Take Availability release.
Known Issues
Installation and configuration
- The .rpm installation packages do not verify that they are being installed on the correct operating system version or distribution. For example, the .rpm file for Red Hat Enterprise Linux version 5.0 can be installed on a version 4.0 system, even though it will not run on that system. Make sure you are installing the correct .rpm file for your operating system.
- The Double-Take Availability configuration file /etc/DT/DT.conf is initially blank. To populate it with default values, start and stop the Double-Take daemon once.
- Double-Take Availability does not directly support nested mount points. If you mount one mount point as DTFS, that mounting will not extend the DTFS layer to the nested mount points. You must mount each mount point as DTFS individually, when using a nested mount point configuration.
- Red Hat version 4.5 has an issue where the gam_server process uses too much or possibly all of the available CPU. Double-Take Availability may increase the exposure of the gam_server issue, and in return the gam_server issue may decrease Double-Take Availability performance. Additionally, gam_server requires a server reboot when unmounting a replication mount point. Double-Take Software has confirmed an available patch resolves these gam_server issues. If you experience these issues, you should consider applying the patch. For more details, see the Red Hat bug report at https://bugzilla.redhat.com/show_bug.cgi?id=240154.
- The IP table configuration options in DTSetup do not work in this release. Opening the ports will return an error. Closing the ports will return a successful message, although no ports will be closed. To work around this issue, use native operating system tools or another method to manually open and close the ports for Double-Take Availability communication. This issue may be resolved in a future release.
- DTFS mounts should remain mounted for the duration of the system uptime, if possible. Any file handles that a process has open on a DTFS mount location before DTFS is mounted will not be captured by replication. Since DTFS mounts are not automatically unmounted when the Double-Take daemon is stopped, the command service DTMount stop can be used to stop all DTFS mounts, if necessary.
- If you uninstall the software while there is an active Double-Take Availability connection, you must reboot the server before reinstalling the software again. This issue may be resolved in a later release.
- DTFS will fail to mount on fifth subdirectory levels and lower and on directories with a space in the name. These issues may be resolved in a future release.
- Double-Take Availability currently does not support FTP servers configured for chroot or a chroot jail.
- If you are using SLES version 9.x and you want to export /data over NFSv3 and you have DTFS mounted at /data/dtfs, you may find that your NFS clients cannot see any data in /data/dtfs. To work around this issue, include both /data and /data/dtfs in your /etc/exports file.
- If you are protecting your entire server, SELinux should be disabled on the source and target. This limitation may be resolved in a later release.
Replication
- If you want to include root as a replication mount point, you must configure a full-server protection connection. If you want to establish a data-only connection, then do no select the root as a replication mount point.
- The Replication Console will display all mount points capable of supporting replication. Those that have been mounted for replication will be identified as DTFS mount points. Select data from these mount points for replication. If the mount point you want is not labeled as DTFS, you must mount it for replication through the DTSetup utility. Mounting can occur without restarting the daemon.
- If you have hard links in your replication set, note the following caveats.
- The verification report will not display the full attributes. This issue may be resolved in a later release.
- If there are hard links outside the replication set or DTFS mount that link to files inside the replication set, Double-Take Availability will not mirror or replicate the hard links which could lead to differences on the target.
- If the kernel's dcache does not contain a reference to a hard link Double-Take Availability is attempting to use, replication operations will be missed causing inconsistent data on the target. If this happens, a remirror will be required.
- Two replication operations are sent when a file is closed. This may have a negative effect on performance. This issue may be resolved in a future release.
- Replication sets should only include necessary data. Including data such as temporary files, logs, and/or locks will add unnecessary overhead and network traffic. For example, if you are using Samba, make sure that the location of the lock file (lock dir in samba.conf) is not a location in your Double-Take Availability replication set.
- Directories with an asterisk (*) in the name will not be replicated. This issue may be resolved in a future release.
- Do not attempt to mount too many DTFS mounts (50 or more). You will receive a buffer overflow error. This issue may be resolved in a future release.
General functionality
- If you specify NoMoveAddresses with the MonitorOption DTCL command, the addresses will still be moved after failover. This issue may be resolved in a later release.
- When you schedule start criteria for transmission, you may see the transmission status in an error state at the scheduled start. The transmission will still continue as expected. This may be resolved in a later release.
- When you schedule a verification process, it may run a verification report when you save the scheduled verification settings. The scheduled verification will still process as expected. This may be resolved in a later release.
- If you are moving or deleting orphan files, keep in mind the following caveats.
- Long path names will not be removed. This may be resolved in a later release.
- Select a move location outside of the replication set. If you select the location where the files are currently located, the files will be deleted. If you select another location inside the replication set, the files will be moved multiple times and then possibly deleted.
- The Log Orphaned Files to Target List option on the Connection Manager, Orphans tab is dependent on moving or deleting the orphan files. It does not function on its own.
- Files that were open or being accessed at the time of failover will generate Stale NFS file handle error messages. Remount the NFS share to correct this error.
- If you are using Red Hat Enterprise Linux version 4.x, do not export NFS on any subdirectories below where you mounted the DTFS driver, otherwise the source server will stop responding and you will have to reboot it. If you need to export NFS, do it at the parent directory. This is not an issue on Red Hat Enterprise Linux version 5.x. This issue may be resolved in a later release.
- Before verifying your Double-Take Availability data, make sure that source applications are inactive and that files in the replication set are not open. Otherwise, the verification process may show differences between the source and target.
- During failover, the IP addresses of the source are added to the target, but they are not persisted. The IP addresses will be lost if the target is rebooted. To work around this issue, configure persistent source IP addresses. This issue may be resolved in a later release.
- The ability to stop transmission based on a specified byte limit is currently not functional. This issue may be resolved in a later release.
Clients
- If you are using the Failover Control Center, you must have host entries or DNS entries for the servers and the client machine in order to login to a server.
- When configuring failover monitoring in the Failover Control Center, if you enter an IP address in the Insert Source Machine dialog, you will be prompted that the server could not be located. After you click OK on the error message, the server will still be inserted in the Failover Control Center correctly (assuming the server can indeed be reached). Click Cancel to exit the Insert Source Machine dialog box and continue with your failover monitoring configuration.
- The interactive text client (DTCL -i) may intermittently fail if there is no DNS entry or way for a server to resolve server names.
Documentation
- In order to view the online documentation, you must have one of the following browsers.
- Internet Explorer 5.5 or later
- Mozilla Firefox 1.0 or later
Contact Information
- Product Updates—Check your service agreement to determine which updates and new releases you may be eligible for. Product updates can be obtained from the Double-Take Software support web site.
- Sales—If you need maintenance renewal, an upgrade activation code, or other sales assistance, contact your reseller/distributor or a Double-Take Software sales representative. Contact information is available on the Double-Take Software web site contact information page .
- Technical Support—If you need technical assistance, you can contact technical support. All basic configurations outlined in the online documentation will be supported through technical support. Your technical support center is dependent on the reseller or distributor you purchased your product from and is identified on your service agreement. If you do not have access to this agreement, contact Double-Take Software Technical Support and they will direct you to the correct service provider. To contact Double-Take Software Technical Support, you will need your serial number and activation code. Contact information is available on the Double-Take Software web site support information page.
- Professional Services—Assistance and support for advanced configurations may be referred to a Pre-Sales Systems Engineer or to Professional Services. For more information, see the Double-Take Software Professional Services information page.
- Training—Classroom and computer-based training are available. For more information, see the Double-Take Training information page .
- Documentation—Please forward any comments or suggestions about this online documentation to documentation@doubletake.com.
Double-Take, Balance, Double-Take Availability, Double-Take Backup, Double-Take Cargo, Double-Take Flex, Double-Take for Hyper-V, Double-Take for Linux, Double-Take Move, Double-Take ShadowCaster, Double-Take for Virtual Systems, GeoCluster, Livewire, netBoot/i, NSI, sanFly, TimeData, TimeSpring, winBoot/i and associated logos are registered trademarks or trademarks of Double-Take Software, Inc. and/or its affiliates and subsidiaries in the United States and/or other countries. Microsoft, Hyper-V, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. All other trademarks are the property of their respective companies.
© 1996-2010 Double-Take Software, Inc. All rights reserved.